Aminet 19

home *** CD-ROM | disk | FTP | other *** search

/ Aminet 19 / Aminet 19 (1997)(GTI - Schatztruhe)[!][Jun 1997].iso / Aminet / comm / cnet / INetShell308b.lha / INetShell / INetShell.doc < prev next >

Wrap

Text File | 1997-03-13 | 48KB | 1,131 lines

/*****************************************************************************\ |*****************************************************************************| |*****************************************************************************| |*** ***| |*** INet-Shell: A utility to offer a simple-to-use interface between ***| |*** AmiTCP/IP and CNet Pro v3.xx ***| |*** ***| |*** INet v3.08 01/28/97 (AREXX - compiled) ***| |*** # INetConfig v3.03 03/27/96 (SAS/C - v6.56) ***| |*** # INetMaint v3.12 03/27/96 (SAS/C - v6.56) ***| |*** ***| |*** # - NOT YET UPDATED FOR USE WITH CNET VERSION 4.XX ***| |*** ***| |*** RELEASE DATE: 01/28/97 ***| |*** ***| |*** Original concept and programming performed by: ***| |*** ***| |*** Paul Leclair (Limahl) ***| |*** limahl@ime.net ***| |*** ***| |*** Continued support and updates, and conversion to CNet/C by: ***| |*** ***| |*** Andy Dickison (Seahorse) ***| |*** seahorse@dcroads.com ***| |*** seahorse@1:270/617.0 ***| |*** ***| |*** Information, updated, technical support can be obtained at: ***| |*** ***| |*** Digital Crossroads BBS ***| |*** ***| |*** (717)843-7465 - 5 lines USR v.everthing 33.6K ***| |*** TELNET/FTP/WWW @ dcroads.com ***| |*** ***| |*****************************************************************************| |*****************************************************************************| \*****************************************************************************/ A special thanks to Paul Leclair for allowing me to continue his fine work on this program. And his continued support with new ideas. If you have any comments, please E-Mail them to me at: seahorse@dcroads.com dcroads@netrax.net Also thanks go to the beta-testers: (none currently being used) /*****************************************************************************\ |* NOTES ABOUT CONTINUEING DEVELOPEMENT *| \*****************************************************************************/ INetShell 3.xx is currently being rewritten in C. The Arexx source was released some time ago and the conversion process has begun. Currently, the only programs available are INetConfig and INetMaint. INetConfig is not completed, but is required and has all of the pervious config entries available. The new INetConfig is needed to configure the new flags for INetMaint. INetMaint is basically completed. There may be some enhancements made in a future release, but it's VERY functional as it stands. No completion date has been set as it's a bit early to date this project completion. So, please do not send me a ton of email asking me when will it be done. ;-) I will keep you all posted. /*****************************************************************************\ |* ABOUT INET-SHELL *| \*****************************************************************************/ Originally conceived by Paul Leclair (Limahl) and support continued by Andy Dickison, INet-Shell, is one of the view interfaces available for CNet Amiga Pro 3.xx that provides and easy to use interface between CNet BBS and AmiTCP/IP, therefore allowing your users to fully access the growing services on the Internet with relative ease. INet : Is the heart and soul to INet-Shell, it is the actual interface that your users will use for accessing the internet. Presently written and compiled in ARexx. It is being rewritten as a CNet/C PFile with SAS/C v6.56 its release date at this time, is unknown. INetMaint : "INetMaint" is a CNet/C utility that performs serveral vital maintenance items associated with INet-Shell. - Purges old INet directories from users how have been deleted from your system and still have an INet FTP directory setup. - Removes the users entry from the db/passwd file. - Can purge files older than a set date from each users FTP direcotory. - Can provide a log to any or all of three different locations: sysops mailbox, call log, and/or the maintenance log. Written as a CNet/C PFile with SAS/C v6.56. INetConfig: This is the program that you will use to configure the necessary options to allow both INet and INetMaint to run properly and to your desires. Written as a CNet/C PFile with SAS/C v6.56. /*****************************************************************************\ |* LEGAL STUFF *| \*****************************************************************************/ COPYRIGHT INFORMATION: The program, INetShell and its associated files are written and copywrited by Andy Dickison (CND Communications). INetShell is SHAREWARE and the UNREGISTERED version may be freely distributed providing the following conditions hold: o Distributors may not charge more than the cost of a diskette used in the distribution of this program. o Distributors may only distribute the unmodified copy of the original program, along with all of its documentation, and copywrite notices intact. o Commercial distribution is only possible with written permission from the author. LICENSE AGREEMENT: The REGISTERED versions of INetShell may not be redistributed. Redistribution is illegal, immoral, and strictly prohibited. The licensed keyfile is good for only a single copy of CNet Amiga (c)ZenMetal. DISCLAIMER: This program and its documentation are provided "as is". No warranties are made with respect to the accuracy, reliability, performance or operation of this software and information. You are using this program at your own risk. The author is not liable for any damages that may have been caused by using this software. /*****************************************************************************\ |* INSTALLATION *| \*****************************************************************************/ This will explain how to install the INetShell. ------------------------------------------------------------------------------- o Unarchive the INet Shell archive to an empty directory (lha -a x). ------------------------------------------------------------------------------- o Create a directory in SysData: called DCROADS. Place the keyfile that you have obtained from me in SysData:DCROADS/. Failure to do so, will prevent proper opertion of INetShell. ------------------------------------------------------------------------------- o Verify that the pure bits on the executables INET, INETMAINT, and INETCONFIG are set, as all three programs CAN be made resident and are compiled pure. ------------------------------------------------------------------------------- o Make a directory in PFILES: called "INetShell" ------------------------------------------------------------------------------- o Copy the contents of the archive into Pfiles:InetShell/ (For those of you upgrading from a previous version, ensure that ALL of the contents of of the config file are present or you WILL run into problems). ------------------------------------------------------------------------------- o Be sure that the "PURE" bit (p) is set on the INet main binary. (ie. protect INet +p) ------------------------------------------------------------------------------- o In your INetShell/config directory, you will find 2 files "INet1.305c" and "INet.4xx" rename the file that is associated with the version of CNet that you are running on your system to INet1. ------------------------------------------------------------------------------- o The main INet-Shell binarys may be made resident to save memory. The format is: "resident PFiles:INetShell/INet PFiles:INetShell/INet pure add" "resident PFiles:INetShell/INetConfig PFiles:INetShell/INetConfig pure add" "resident PFiles:INetShell/INetMaint PFiles:INetShell/INetMaint pure add" ------------------------------------------------------------------------------- o Move the files RPSTART and RPHI in the c/ directory over to C: (do this only if you do not already have them on your system) ------------------------------------------------------------------------------- o Move the rexxplslib.library in libs/ over to Libs: (do this only if you do not have this library already) ------------------------------------------------------------------------------- o (Do the following only if you haven't installed Rexx Plus on your machine): o Edit your S:user-startup o Add a line with the command RPSTART >NIL: ------------------------------------------------------------------------------- o If you are updating from any version OLDER than 2.4 then you MUST delete Mail:users/#?/.netrc ------------------------------------------------------------------------------- o If you have been running another kind of interface program or have had users using FTP and have previously set up the .netrc file(s), they must be all deleted. Usually, they will reside in "Mail:users/<dir>". You can delete them all by doing the following command: Delete Mail:users/#?/.netrc ------------------------------------------------------------------------------- o Edit your CNet:BBSMENU file(s) and add the following command to section "1; Maintenance menu": INETCONFIG |{#2 PFiles:INetShell/INetConfig} INETMAINT |{#2 PFiles:INetShell/INetMaint} ^ Control-Q ------------------------------------------------------------------------------- o Save bbsmenu file(s) and reload your BBSTEXT/MENU files from the CNet Control panel. ------------------------------------------------------------------------------- o Run INETCONFIG and setup all of the program defaults/settings. ------------------------------------------------------------------------------- o Edit your cnet:bbsmenu file(s) and add the following command to section to section "3; Main Prompt" NET |{#0 PFILES:INetShell/INet} ^ Control-Q ------------------------------------------------------------------------------- o Save bbsmenu file(s) and reload your BBSTEXT/MENU files from the CNet Control panel. ------------------------------------------------------------------------------- o Set up a directory to store the user's profiles & ftp files (this directory must match the name used in INETCONFIG for the users FTP direcotry). (ie. MAKEDIR <dirname>) Suggestion: use a drive that has a lot of storage because this is where all FTP files end up when a user does an FTP. It is HIGHLY suggested that you do NOT set up the directory to merge with "mail:users/" due to users having the ability to download and/or upload to this directory area. ------------------------------------------------------------------------------- o "NET" should now be configured and ready to go. /*****************************************************************************\ |* NOTES CONCERNING INSTALLATION / COMMON PROBLEMS *| \*****************************************************************************/ ------------------------------------------------------------------------------- PROBLEM : Running FTP/ncftp gurus my computer SOLUTION: For proper operation of INetShell FTP Feature, you need to run cnet with a stack of atleast 40000 at this time. ------------------------------------------------------------------------------- PROBLEM : My system freezes after just after I start INetShell, or after the statement "PLEASE ASK YOUR SYSOP TO REGISTER INET-SHELL" for Unregisted versions of INetShell. SOLUTION: AmiTCP/IP users: Make sure that you have INET: assigned to AmiTCP: Miami Users: See problem below for your solution. ------------------------------------------------------------------------------- PROBLEM : I am running Miami as my TCP/IP stack and INetShell freezes just after startup. SOLUTION: Miami Users: INetShell has been shown that it will run under Miami, however, as INetShell was developed around AmiTCP you will need to do the following: o Assign INET: to Miami: o Assign AmiTCP: to Miami: o Create a directory in Miami: called bin o Place all clients used by INetShell in Miami:bin (ncftp, telnet, talkclient, amyirc, lynx, bbgopher, finger, etc) o Last but not least you need to obtain a copy of the AmiTCP program AmiTCP:bin/hostname and place it into miami:bin ------------------------------------------------------------------------------- PROBLEM : Running amyirc either gurus my system or will not work at all. SOLUTION: To get amyirc running correctly the following needs to be done: o Rename the amyirc program to aamyirc o Create a script file (S protection flag set) called "amyirc" with the following in it. ---------------- START: CUT HERE ---------------- .KEY ONE,TWO,THREE,FOUR,FIVE,SIX,SEVEN,EIGHT changetaskpri -1 inet:bin/aamyirc <ONE> <TWO> <THREE> <FOUR> <FIVE> <SIX> <SEVEN> <EIGHT> changetaskpri 0 ---------------- END : CUT HERE ---------------- o Create a file in sys:env or sys:prefs/env-archive (depending on verion of amigados) called "socketconfig" with the follwoing information: ---------------- START: CUT HERE ---------------- UID=200 GID=200 USER=dcroads DOMAIN=com UMASK=002 ---------------- END : CUT HERE ---------------- change the "user" to the first part of you domain name and domain to the last. (ie com, org, net, etc). ------------------------------------------------------------------------------- PROBLEM : Lynx will not run on my system SOLUTION: To get lynx running use the following script file "alynx" ---------------- START: CUT HERE ---------------- ;Script for ALynx & INetShell ;written fully by Dave Anderson of Ground Zero Communications (gzero.com) echo "Loading...." cd > T:ll rx amitcp:bin/name delete t:ll quiet execute t:ldir delete t:ldir quiet execute t:hdir delete t:hdir quiet wait 1 amitcp:bin/alynx.exe http://localhost -show_cursor -rlogin -telnet -noprint ---------------- END : CUT HERE ---------------- ------------------------------------------------------------------------------- PROBLEM : BBGopher is unreliable and does not work well. SOLUTION: As I have found bbgopher unrealialbe at this time, I use lynx for gopher as well. To do this: o Rename bbgopher to something you will not use. o Create a script file "bbgopher" with S protection bit set, with the following contents: ---------------- START: CUT HERE ---------------- ;Script for ALynx & INetShell ;written fully by Dave Anderson of Ground Zero Communications (gzero.com) echo "Loading...." cd > T:ll rx amitcp:bin/name delete t:ll quiet execute t:ldir delete t:ldir quiet execute t:hdir delete t:hdir quiet wait 1 amitcp:bin/alynx.exe http://gopher.micro.umn.edu -show_cursor -rlogin -telnet -noprint ---------------- END : CUT HERE ---------------- ------------------------------------------------------------------------------- This should take care of most peoples problems with getting INetShell operational. Please contact me if you have any additional questions. ------------------------------------------------------------------------------- /*****************************************************************************\ |* EDITING AND CONFIGURING INET-SHELLS OTHER DATA FILES *| \*****************************************************************************/ There are 7 types of config files that the shell uses. The files are located in PFiles:INetShell/Config/ TelnetMenu - main list of telnet sites (menu) Telnet# - actual telnet sites FTPMenu - main list of ftp sites (menu) FTP# - actual ftp sites ArchieServ - list of Archie servers IRCServer - list of IRC servers ------------------------------------------------------------------------------- TelnetMenu: TelnetMenu is the primary menu that users see when they first enter the Telnet command off the main menu of INetShell. This is just a list of available sub-menus that the user can enter. There is no limit to how many sub-menus you can create. The format of TelnetMenu is: 2 Menu Item 1 Menu Item 2 Line1: the total amount of entries in the file (excluding line 1) Line2: name of directory Line3: name of directory etc See the example that is packaged with INetShell. ------------------------------------------------------------------------------- FTPMenu: FTPMenu is the primary menu that users see when they first enter the FTP command off the main menu of INetShell. The data format is the same as TelnetMenu. ------------------------------------------------------------------------------- IRCServer: This is a list of IRC Servers that you can reach. The data file format is set up like so: 1 IRC Server (US) irc.pitt.edu Line1: number of total servers listed Line2: Name given for the server (the name that will show up on the server listing) Line3: the actual server domain name or IP#. See the example IRCServer file in the config directory. As with TelnetMenu and FTPMenu, there is no limit to how many servers you may add to this list. ------------------------------------------------------------------------------- ArchieServ: This file contains the available Archie servers that your users can use when doing an Archie file search. The format is: site.name.or.ip site.name.or.ip site.name.or.ip etc etc There is a maximum of 8 sites you can have listed. This may change in the future if there is a need for a larger list. Note that this file format does NOT contain the # of sites at the start. It only contains the domain or IP# of the Archie server site. ------------------------------------------------------------------------------- Telnet#: The Telnet(number) file(s) contain the actual sites and descriptions of the Telnet sites. These files are connected with the TelnetMenu file. Here is how it works: If in TelnetMenu, you have 3 entries, you must have 3 Telnet# files (Telnet1, Telnet2 & Telnet3). When the user picks item 1 off the main Telnet list, it will load up and display the Telnet1 sub-menu. The format is: 1 The Kobayashi Alternative BBS tka.com 23 This is a CNet BBS and home of the INetShell interface program. Line0: Total number of sites in list Line1: Name of the Telnet Site Line2: the domain.name or IP# and (optional) port number Line3: description line 1 Line4: description line 2 Line1: Line2: LIne3: Line4: Please note, if you use the TELNET client that comes with the the INet package, passing a parameter "-m1" before the site name will cause Telnet to go into "mud mode" which is basically an echo character mode. Note, you MUST have 2 description lines before the next entry. These can be blank lines if you wish not to have any description listed. There is no limit to how many sites you can have listed in these files. ------------------------------------------------------------------------------- FTP#: The FTP(number) file(s) contain the actual sites and descriptions of the FTP sites. These files are connected with the FTPMenu file. The format and how it works is the same as the Telnet# files. ------------------------------------------------------------------------------- =============================================================================== WHAT IT DOES: What happens when a new user gets into the INetShell: 1. The program will check to be sure that they have a valid Internet Name (UUCP ID). If this has never been set, it will ask the user to enter a name or auto-set the ID depending on what config variable the sysop has chosen for this. 2. The program will then create the user's FTP storage directory in the location you specified in the "INet" config file. 3. It will then copy the default "." files from the INetShell/new/ directory into their FTP storage directory. 4. It will then create a .netrc with default settings in the user's "mail:users/<dir>" area. 5. Then it will maintain the AmiTCP:db/passwd file (as specified in the INet config) and add an entry for their account. 6. Finally it will let them into the main menu. =============================================================================== ACCOUNTING & UNLIMITED TIME FEATURE: INet has the ability to give a user unlimited time while they are in the shell program itself without disturbing the user's daily allowed time per day. This flag can be set in INetConfig. Also, INet can calculate a balance total for usage within the shell itself. This was set up for those sysops who use the CNet Accounting system to keep track of different areas of their system. In this case, INet will calculate the amount of time by the amount to charge (see INetConfig's entry for Accounting costs) and then subtract that from the balance on the user's account when they exit INetShell (or drop carrier - whichever comes first). =============================================================================== SHELL FEATURE (V2.5+) In version 2.5 and up, a SHELL/Expert Mode option has been made for users who are familiar enough with Telnet/FTP and such to use command line prompting rather than the menu system. As a bonus to this shell mode are the clients "ASKHOST", "RESOLVE", and "TRACEROUTE". These utility clients must be in your AmiTCP:bin/ directory in order for them to work properly. =============================================================================== NOTES ON THE TALK CLIENT FOR INETSHELL: The newest addition to INetShell is the Talk client. This client gives your users the ability to "talk" in a split-screen window with someone else on the the Internet. It's similar to CC-Chat. From the tests I've run on my system, it does support CTRL-C drops very well and has never crashed m board. The The version we're running is 1.53 of AmiTALK (available on AmiNet). What I suggest is that you install AmiTALK according to the docs included with the archive and configure it so that the "TALK" command is available from any prompt. I believe the instructions are included in the archive to have this work. This is so that if a user on another system is requesting a "TALK" session with you, you will be able to start TALK up without having to go into INetShell to do it. If you run into any problems with the Talk client, just rename it to something else. This will disable the feature - when the client gets called. =============================================================================== BUGS & ERROR REPORTS: Should the program have a programming error (GOD FORBID!), it will report it in E-Mail to User ID#1 (usually the sysop). Please forward this mail file to me at my Internet address (dcroads@postoffice.ptd.net). Note that the program may and will error out should you run the ARexx "halt" (hi) command. Usually, it will give some kind of syntax error. The next release (1.5) should have this taken care of. /******************************************************************************\ |* INET UPDATE HISTORY *| \******************************************************************************/ PROGRAM NAME: INet PURPOSE : To offer a simple-to-use interface between AmiTCP/IP and CNet BBS users. RELEASED : 01/28/97 VERSION : 3.08 ------------------------------------------------------------------------------- REVISIONS : 3.08 (01/28/97) - Updated INet1 executable for versions 4.24g and 4.24h of CNet. - Updated copywrite date. 3.07 (12/17/96) - Formats INetShell usage log so it is now easier to read. - INet1 executables now contain version strings, by using version full INet1(.xxx) it is easy to tell which version of CNet this is for. - Some users still having problems with INetShell not recognizing a valid registered copy. Have made some some changes to code, in hopes that this will fix the problem. INet-Shell works fine on my system(s) for both CNet 3.05c and CNet 4.24d. - Updated INet1 for version 4.24d of CNet. - Created subdirectories RAM:INetShell/Config and RAM:INetShell/Text for preperation of C version. 3.06 (09/03/96) - Found a problem with CNet not properly updateing the UUCP ID pointers in memory, after being changed either manually or automatically via INetShell under CNet v4.xx. This problem with INetShell has been fixed. - Recompiled INet1.421 for use with CNet Amiga version 4.21 Beta. - Problem reported with one version of animated more prompt preventing proper keyfile checking. Added a command to disable more prompt first thing in program execution. This should fix this problem/bug. - Fixed MOTD title screen to properly indicate (and give credit) to previous and present author of INetShell. 3.05 (06/28/96) - Created a "Demo" mode. This will allow perspective INetShell users to see what it will do for them. In the "demo mode" only one user online will be able to use INetShell at a time. - Fixed/recompiled keyfile check program for use with v412d of CNet. 3.04 (06/09/96) - Found a problem with the generation of an automatic UUCPID. Pre 3.03 versions of INetShell, use the users handle to generate a UUCP id if the sysop has elected to not let a user select their own. As CNet uses the first letter of the first name and upto 7 letters of a users last name to automatically generate the UUCPID during the first time they logon (v4.11+ of CNet), I have fixed INet shell to do the same. With the added feature that it will generate up to 9999 new UUCPID for duplicate original UUCPID numbers. 3.03 (03/27/96) - Wrote a fix that will make INet compatible with the way Ken had his hex format of Mail:users/???? mailbox setup. This version should ONLY be used for v4.08 - v4.10 of CNet. (Executable name INet.408_410) 3.02 (03/27/96) - FULL INetShell program developement turned over to Andy Dickison. - Put in hostname checking for the purposes of VERIFING that AmiTCP/IP is in operation and allowing users to see what the domain name of the system is at this point in time (added for those few sysops that use INetShell and do not have a permanent INetNet site). - Added keyfile method of maintaining security of registered verisons of program. 3.01 (09/01/95) - Fixed screen clearing problem when returning from the archie server screen. - Removed hostname checking. 3.00 (06/27/95) - Well, it's my birthday today so I just HAD to release another update! - Added the talk client w/new screen. - Fixed a carrier check bug that one of my users so nicely discovered. - Added host checking. If the INetShell hostname doesn't match your system hostname, INetShell will abort - giving an error Hostname mismatch error. - Rewrote the documentation in an AmigaGuide format. - Fixed a config file that was reading from disk even though the COPY-CONFIG-TO-RAM option was set. 2.90 (04/23/95) - Added LYNX to the main menu. - Added Gopher to the main menu. - Restructed the main menu a bit. - Cleaned up a clear screen code that was bugging me. - Fixed a minor bug with the way the options were being chosen from the FTP/Telnet menus. - Included are the archives for ALynx and BBGopher. 2.80 (04/13/95) - Added usage logging (configurable via INetConfig) (logs users who ran INetShell). - Added ability to prevent crashing on reading directories within the user's INetShell FTP storage dir. 2.70 (03/23/95) - Bug fix: At the telnet prompt checking for redirection, I never bothered to check for the -m1 option for MUD mode. It should work fine now (HOPEFULLY). - Also reworked some of the screens to give them a bit more of that 3D look and feel. In the future, when CNet supports RIP, it will have functional buttons. 2.60 (03/20/95) - Bug fix: at all prompts, users were able to redirect output of the client software to any file on your disk (including your sysdata: files if they know CNet and its data files. This has been fixed. 2.5b (03/09/95) - A bug was reported with the DS! routine in Dir-Maint so I put a delay before it returns to the program after the file(s) have been transfered. - Had to change the DS! back to DS and put a carrier check that will hopefully solve the bug with logoff after completion. if this doesn't do it, then I'll have to make DS a sysop configurable option. 2.5a (02/26/95) - Changed IRC routine where it would show the user's real name to their UUCP ID. - Changed the download selected files in Dir-Maint to not allow options like auto-logoff. 2.50 (02/22/95) - Added a SHELL mode for expert users. 2.4a (02/15/95) - Fixed addressing of finger from just "finger" to "amitcp:bin/finger" 2.40 (02/07/95) - Did more work for the unlimited time options to fix another bug that I overlooked. - Changed the prompt for ncftp to display system time - Added mprompt feature for mget prompting in config and .netrc (must delete ALL old .netrc's) 2.30 (02/01/95) - Fixed some nasty errors in the accounting calculations which resulted in subracting more time than it should have been (thanks to jrobbins@proton.com for finding this). - Cleaned up the display on accounting so that the decimal points line up. - Reworked the clock/timer routine a bit so that it works correctly in minutes and % of minutes (like how CNet displays # of minutes used). - Checked to be sure that the .netrc gets deleted should the user decide to change their UUCP ID via EP;12. 2.20 (01/16/95) - Added unlimited time for users in configurations. - Added options to copy all config files to ram. - Added sysop maint deactivates limit on FTP dir. - Added configurations for charging via CNet Accounting. 2.1b (01/06/95) - Fixed bug for creating new users and not having the correct passwd file entry. 2.1a (01/01/95) - Added DirMaint storage directory size limit configurable from INetConfig demo version created from 2.1a release. 2.00 (12/28/94) - FINAL version - ready for release! - Debugging some more code. - Adding security checks (system hostname). 1.6e (12/28/94) - Fixed the aposthrophie bug in the notebook (yippee!). - Added 2 new screens (telnet/ftp) for manual dialing. 1.6d (12/27/94) - Added Upload function (configured by INetConfig). - Fixed annoying bug in Edit routine (renaming files). 1.6c (12/25/94) - Shortened subroutine names and compiled (pure bit set) for speed. 1.6b (12/23/94) - Fixed some of the input strings to lock out the use of double quotes ("). - Compiled with Rexx Plus for speed. 1.6a (12/22/94) - Reworked the downloading routines to allow users to download just individual files without having to tag them first (saving a step) 1.60 (12/22/94) - Added a new sysop definable config in the INET config file to allow optional setting for creating new usesr accounts. - Added INET config entry to allow sysops to force a new user news file to be displayed when new users create an account. - Added INET config entry to set MOTD displaying before a user gets to the main menu. (This is toggled on/off by the user in the Configurations menu.) 1.50 (12/21/94) - Added a few more checks for drop carriers. - Added a halt routine for sysop forced HI's. 1.40 (12/19/94) - Added a VIEW option in Directory Maintenance to view files. - Altered the dropcarrier routines so that they all check at the appropriate places. 1.30 (12/18/94) - Set up error logging to send email to CNet ID#1. 1.20 (12/17/94) - Added the "C" command in IRC to allow users to change handles without having to quit IRC mode. - Updated some of the display screens for a better 3D look. 1.10 (12/16/94) - Fixed a minor screen clearing routine that was happening twice for no reason. 1.00 (12/15/94) - Finished 1st version of program. 0.00 (11/21/94) - Initial creation of program. /******************************************************************************\ |* INETCONFIG UPDATE HISTORY *| \******************************************************************************/ PROGRAM NAME: INetConfig PURPOSE : To allow editing of ALL the various configuration items associated with INetShell. - Basic configuration items. $ - Permenant UUCP accounts in the AmiTCP passwd file. $ - Telnet Sites. $ - FTP Sites. ($ - NOT YET IMPLEMENTED) RELEASED : 03/27/96 VERSION : 3.03 ------------------------------------------------------------------------------- REVISIONS: 3.03 (03/27/96) - Changed version number ONLY, to more easily keep track of which version series will work properly with the versions of CNet BBS. 2.01 (09/12/95) - Fixed a problem with the save routine/read config routine. 2.00 (09/11/95) - Rewritten in C. - Allows modification of FTP file age limit. - Allows modification of flag to delete old FTP files. - Gets BBS Name from CNet Configuration, and no longer allows sysop to edit it from INetConfig module. - Added version string. - Added flag to log INetMaint activity to call log. - Added flag to log INetMaint activity to maint log. - Added flag to log INetMaint activity to a specified users mail box. 1.40 (04/13/95) - Added usage log option #6. 1.30 (01/16/95) - Added copy to RAM: for config dir. - Added unlimited time option for INet. - Added accounting features. 1.20 (01/01/95) - Added DirMaint limit (Ftp storage dir). 1.10 (12/30/94) - Added INetMaint options (2nd screen). 1.00 (12/25/94) - Initial creation of program. /****************************************************************************\ |* INETMAINT UPDATE HISTORY *| \****************************************************************************/ PROGRAM NAME: INetMaint PURPOSE : To delete old FTP directories from users who hoave been purged from the system. To delete old FTP files (dated older than preset date) from the FTP directories of active users. To maintain the PASSWD file used by AmiTCP, removing inactive UUCP entries, and duplicates. RELEASED : 03/27/96 VERSION : 3.12 NOTE: THIS VERSION WILL NOT WORK PROPERLY WITH CNET V4.08 - V4.10 AND I HAVE NO INTENT OF PRODUCING A FIX FOR THESE VERSIONS OF CNET AS ANYONE THAT IS STILL USING IT IS A FOOL. :) ------------------------------------------------------------------------------- REVISIONS: 3.12 (03/27/96) - Version number change only, to correspond with the version of CNet that it is compatible. 2.12 (09/23/95) - Fixed problem with INetMaint tring to delete directories from within a users FTP Dir. 2.11 (09/12/95) - Updated structures to conform with those changed in INetConfig. 2.10 (09/11/95) - Added version string. - Rewrote file reading routines (should make passwd file maintenance routines faster). - Logs name of any "old" FTP files that are deleted during maintenance. - Added ability to log activities to the Call Log as determined by INetConfig settings. - Added ability to log activities to the Maint log as determined by INetConfig settings. - Added ability to log activities to a specified users mail box. - Included a check to verify account message to be sent to, is still active, if not, mail will be sent to user # 1 2.00 (09/03/95) - Rewritten in C. - Added ability to delete old FTP files from user direcoties. - Added ability to update AmiTCP PASSWD file, both removing inactive entries, and duplicates. - Added a means to allow upto 100 for "permanant" PASSWD file entries. - Added a rudimentary progress report, by outputing maint actions to terminal screen. - Writes maintenance actions to the call log. 0.00 (12/29/94) - Start of program /****************************************************************************\ |* NOTES ABOUT v4.08 - v4.10 of CNet BBS *| \****************************************************************************/ First off, why Ken changed the Mail:Users/????? directories to hex I haven't a clue. But when he did this, he basically screwed INetShell. In this archive, you will find 2 version of the INet Executable. INet : Usable for pre 4.08 and post 4.10 versions of CNet INet.408_410 : Usable for ONLY v4.08 - v4.10 of CNet (Available at FTP site, left out of distribution for space considerations) Additionally do NOT use the included version of INetMaint with v4.08 - v4.10 of CNet, as it will totally screw up your users ftp directories by deleteing each and everyone of them. I have no intent of releasing a version of INetMaint that will work under these versions of CNet as the problem nolonger exists under 4.11+, and any one that is still using v4.08-4v4.10 of CNet is asking for trouble. ];-) One other additional change must be made with your configuration files to make INetShell properly use Lynx under 4.08-4.10. Useing you favorite text editor load in the Lynx script (and or bbsgopher script as I use lynx for both web and gopher browsing) make the folling change(s) so that the script looks like the following. ---------------------------- ;Script for ALynx & INetShell ;written fully by Dave Anderson of Ground Zero Communications (gzero.com) echo "Loading...." ;cd > T:ll <------------ NOTE THIS IS THE ONLY LINE TO CHANGE rx amitcp:bin/name delete t:ll quiet execute t:ldir delete t:ldir quiet execute t:hdir delete t:hdir quiet wait 1 amitcp:bin/alynx.exe http://localhost -show_cursor -rlogin -telnet -noprint ---------------------------- For use of lynx with gopher, I change the last line of this script to: amitcp:bin/alynx.exe http://gopher.micro.umn.edu -show_cursor -rlogin ~ ~ -telnet -noprint ---------------------------- This is all that I can think of at this point in time. Contact me if you run into any additional problems. Seahorse / Andy Dickison seahorse@dcroads.com dcroads@netrax.net seahorse@1:270/617.0 /****************************************************************************\ |* UPGRADING INETSHELL FROM 3.01 OR EARLIER *| \****************************************************************************/ Make sure that you copy the INetShell/Config/INET1 program from the archive into pfiles:inetshell/config and ram:inetshell. Or INetShell will not come up correctly. /****************************************************************************\ |* HOW TO REGISTER INETSHELL *| \****************************************************************************/ To get a registered copy of INetShell, send $25.00 (US) (certified bank check or money order - no personal checks or cash) to: CND Communications PO Box 7410 York PA 17404-0410 RE: INetShell Please make the check payable to: CND Communications And please fill out and mail in the following form with your order: ============================================================================ I N E T S H E L L R E G I S T R A T I O N ============================================================================ REAL NAME:______________________________________________ POSTAL ADDRESS:______________________________________________ ______________________________________________ ______________________________________________ HANDLE:______________________________________________ BBS NAME:______________________________________________ BBS PHONE:______________________________________________ FIDO ADDRESS:______________________________________________ BBS DOMAIN NAME/IP:______________________________________________ SOFTWARE PACKAGE YOU ARE USING (choose one): [ ] AmiTCP 3.0Beta2 [ ] AmiTCP 4.0 (beta) [ ] AmiTCP 4.x (registered) [ ] AS225 [ ] DNet [ ] Miami HOW DO YOU WISH TO GET YOUR REGISTERED VERSION KEYFILE (ie. FTP'd, US-Snail Mail - choose one): [ ] FTP : dcroads.com FTP site [ ] US-Mail (slower) OTHER COMMENTS: NOTES: Upon completion of the C version there will be a $10 upgrade fee. ========================================================================= /****************************************************************************\ |* HOW TO CONTACT THE AUTHOR *| \****************************************************************************/ I can be reached at: (Please entitle you message INetShell for faster response) seahorse@dcroads.com (having problems with internic so this may not work) dcroads@netrax.net seahorse@1:270/617.0 WW/FTP/Telnet are all available at: dcroads.com (having problems with internic so this may not work) or IP 204.186.35.16 /****************************************************************************\ |* KNOW BUGS WITH INETSHELL ITSELF *| \****************************************************************************/ CNet 4.24d: None Known CNet 3.05c: If you allow your users to change their UUCPID then the will be unable to read there mail until their next logon. This is not a problem with INetShell, but a problem with CNet 3.05c (try editing your UUCPID via "ea" and then to read you mail).